Method and apparatus for controlling service traffic in a communication network

ABSTRACT

A method and corresponding apparatus for controlling service traffic in a communication network comprising in an online charging system performing the steps of receiving a request for service traffic control, the request including at least data identifying a first communication network account; determining, based on the received data and a predefined set of rules, a first network traffic policy profile associated with the first account; transmitting to a Policy and Charging Rules Function PCRF a first policy control command including an identifier identifying the first network traffic policy profile stored in an network traffic policy profile entity, to be applied in controlling the service.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application No.61/472,383, filed Apr. 6, 2011, and to European Patent Application No.EP11163738.5, filed Apr. 26, 2011, the disclosures of both of which areincorporated by reference herein in their entirety.

FIELD OF INVENTION

The present invention relates to a method and apparatus for controllingservice traffic in a communication network.

BACKGROUND

Operators of communication networks face a challenge in how to securemobile broadband revenues.

The tremendous uptake in mobile broadband subscribers and data volumewill require substantial investments in operators' telecominfrastructure. On the other hand, users will expect their operator todeliver the service experience they have paid for. Thus, operatorrevenues from mobile broadband rely on satisfied customers.

A small fraction of the users generates traffic exceeding those ofnormal users with magnitude. In many networks, these heavy users areconsuming a quite large part of the network resources today. Experienceshows that heavy users normally constitutes of 5-10% of the totalsubscribers, but could consume 70-85% of the network resources. It hasbeen shown that often the heavy users are the biggest consumers of thenetwork resources also during busy hour. With policy control operatorscan distribute the traffic load more evenly, giving a defined Quality ofService QoS, e.g. more bandwidth resources, for the normal users (themajority of the subscribers), particularly during the busy hour. Policycontrol also enables operators to push the heavy user traffic into thenon-busy hours where number of normal users is lower. For some heavyuser applications, time of day is not very critical since they click todownload and leave the application running for hours or even days beforecompleting a larger download. Policy control therefore helps controllingnetwork capacity utilization by managing the traffic in a smarter way.

Today and in the future, operators are introducing new premium services,for example ring tones download, TV, video streaming, VoIP, etc. To makesure that the subscribers get the best end user experience whileconsuming these premium services policy control is used to allocate morebandwidth for these applications when being accessed.

Operators use policy control to move away from a blanket, flat fee foreveryone, to the right price for the right service at the right timeensuring users get the user experience paid for. This gives consumersthe chance to choose a subscription that best meets their circumstancesand decide how to act when the subscription doesn't meet their current,specific needs.

For operators, policy control makes it possible to get the most valuefrom their bandwidth, by leveraging the right price for the rightservice at the right time.

In order to handle policy control and charging, the 3rd GenerationPartnership Project 3GPP has in TS 23.203 specified a policy andcharging control PCC functionality encompassing the two main functions:

-   -   Flow Based Charging, including charging control and online        credit control;    -   Policy control (e.g. gating control, QoS control, QoS signaling,        etc.).

The PCC functionality is comprised by the functions of the Policy andCharging Enforcement Function PCEF, the Bearer Binding and EventReporting Function BBERF, the Policy and Charging Rules Function PCRF,the Application Function AF, the Online Charging System OCS, the OfflineCharging System OFCS and the Subscription Profile Repository SPR or theUser Data Repository UDR.

The PCC architecture extends the architecture of an IP ConnectivityAccess Network IP-CAN, e.g. GPRS, where the PCEF is a functional entityin the gateway node implementing the IP access to the Packet DataNetwork PDN.

The PCRF is the part of the network architecture that aggregatesinformation to and from the network supporting the creation of rules andthen making policy decisions for subscribers active on the network.

However, the 3GPP PCC architecture does not provide for the OCS toenforce a QoS thereby addressing the need for a solution which ensuresthat a network traffic policy is applied to the users' traffic, with thepolicy depending on what service the customer has purchased therebyavoiding congestion in the network.

An example is dividing the level of services into service packageproducts such as “gold” (e.g. 3 Mbps, 10 Gb per month), “silver” (e.g.512 kbps, 1 Gb per month) and “bronze” subscriptions (e.g. 128 kbps, 500Mb per month), where at a higher cost, faster service and greateravailable capacity is provided.

A problem is that frequent changes in network traffic policies impactsnetwork behavior thereby risk causing network instability.

SUMMARY OF INVENTION

An object of invention is to provide a method and apparatus forcontrolling service traffic in a communication network avoiding theabove mentioned problem of that changes in network traffic policiesimpacts network behavior thereby risk causing network instability.

The invention relates to a method for controlling service traffic in acommunication network comprising in an online charging system performingthe steps of receiving a request for service traffic control, therequest including at least data identifying a first communicationnetwork account; determining, based on the received data and apredefined set of rules, a first network traffic policy profileassociated with the first account; transmitting to a Policy and ChargingRules Function PCRF a first policy control command including anidentifier identifying the first network traffic policy profile storedin an network traffic policy profile entity, to be applied incontrolling the service.

It may be an advantage of the invention that with the separation ofnetwork policy profiles and user policies, the configured network policyprofiles can be left unchanged when new end-user offerings are createdby the network operator. This means that new types of subscriptions andoffers can be implemented quicker and with less network impact.

It may also be an advantage that it is possible to avoid executingselection rules in both a PCRF and an OCS to determine policy data andcharging data respectively thereby reducing both computing capacityneeds and risk for different decisions due to non-synchronized rules.

It may be another advantage of the invention that when changing chargingrates and quality of service for a service, only one system needs to beprovisioned.

The method for controlling services in a communication network maycomprise before the step of determining a network traffic policy profiledetermining, based on the received data, a service package associatedwith said account to which said service relates; and wherein the step ofdetermining the network traffic policy profile comprises thedetermination being based on an association between said service packageand the network traffic policy profile.

This may have the significance that a network policy relevant for thepurchased service package product can be identified and applied.

The method for controlling services in a communication network mayfurther comprise also that the received request for service trafficcontrol further includes an access network charging address and anaccess network charging identifier and the method further comprises thesteps: receiving from a Packet Gateway a request for credit control of aservice including a packet gateway address and a charging identity;determining a second account to charge for the service; determining thatthe received requests for service traffic control and credit controlrelates to the same service instance by matching the access networkcharging addresses with the packet gateway address and matching theaccess network charging identifier with the charging identity;determining that the second account to charge differs from the firstaccount; determining, based on the received data and the predefined setof rules, a second network traffic policy profile associated with thesecond account; and transmitting to the PCRF a second policy controlcommand including an identifier identifying the second network trafficpolicy profile stored in a second network traffic policy profile entity,to be applied in controlling the service.

This has the advantage that following a charging decision changing theselected account, the network policy relevant for the new selectedaccount may be identified and applied.

Another aspect of the invention relates to an online credit controlsystem OCS for controlling service traffic in a communication networkcomprising an interface module adapted for receiving a request forservice traffic control, the request including at least data identifyinga first communication network account. A determination module is adaptedfor determining, based on the received data and a predefined set ofrules, a first network traffic policy profile associated with the firstaccount. The interface module is further adapted for transmitting to aPolicy and Charging Rules Function PCRF a first policy control commandincluding an identifier identifying the first network traffic policyprofile stored in an network traffic policy profile entity, to beapplied in controlling the service.

The OCS may include that the determination module is further adapted to:before determining a network traffic policy profile determining, basedon the received data, a service package associated with said account towhich said service relates; and wherein determining the network trafficpolicy profile comprises the determination being based on an associationbetween said service package and the network traffic policy profile.

The OCS may further include that the received request for servicetraffic control further includes an access network charging address andan access network charging identifier and the system further comprises:

-   -   The interface module adapted for receiving from a Packet Gateway        a request for credit control of a service including a packet        gateway address and a charging identity.    -   The determination module adapted for: determining a second        account to charge for the service; determining that the received        requests for service traffic control and credit control relates        to the same service instance by matching the access network        charging addresses with the packet gateway address and matching        the access network charging identifier with the charging        identity; determining that the second account to charge differs        from the first account; determining, based on the received data        and the predefined set of rules, a second network traffic policy        profile associated with the second account.    -   The interface module adapted for transmitting to the PCRF a        second policy control command including an identifier        identifying the second network traffic policy profile stored in        a second network traffic policy profile entity, to be applied in        controlling the service.

Embodiments of the invention will now be described in more detail withreference to the enclosed drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a PCC reference architecture accordingto the prior art.

FIG. 2 is a message sequence chart showing an IP-CAN sessionestablishment procedure according to the prior art.

FIG. 3 is a block diagram showing a PCC architecture according to anexemplary embodiment of the invention.

FIG. 4 is a block diagram showing a PCC architecture where exemplaryembodiments of the invention is useful.

FIG. 5 is a message sequence chart showing a method for controllingservices in a communication network according to an exemplary embodimentof the invention.

FIG. 6 is a flow chart showing an exemplary embodiment of a method forcontrolling services in a communication network according to theinvention.

FIG. 7 is a block diagram showing relations between service packageproducts and network traffic policy profiles according to an exemplaryembodiment of the invention.

FIG. 8 is a block diagram showing an exemplary computing device forimplementing a system for controlling services in a communicationnetwork according to an exemplary embodiment.

DETAILED DESCRIPTION OF THE INVENTION

The following detailed description of the exemplary embodiments refersto the accompanying drawings. The same reference numbers in differentdrawings identify the same or similar elements. Also, the followingdetailed description does not limit the invention. Instead, the scope ofthe invention is defined by the appended claims.

FIG. 1 is a block diagram showing a Policy and Charging Control PCCreference architecture 100 according to the prior art 3GPP TS 23.203allowing a User Equipment UE 190 access to a Packet Data Network PDN 195via an IP Connectivity Access Network IP-CAN 185, e.g. General PacketRadio Service GPRS.

The Rx reference point 165 connects the Application Function AF 170 andthe Policy and Charging Rules Function PCRF 120. This reference pointenables transport of application level session information from AF toPCRF

The Gx reference point 150 connects the Policy and Charging EnforcementFunction PCEF 130 of a gateway 135, e.g. a GPRS Gateway Support NodeGGSN, and the PCRF and enables a PCRF to have dynamic control over thePCC behavior at a PCEF. The Gx reference point enables the signaling ofPCC decisions, which governs the PCC behavior.

The Gxx reference point 155 connects the Bearer Binding and EventReporting Function BBERF 160 and the PCRF. The Gxx reference pointenables a PCRF to have dynamic control over the BBERF behavior.

The Sp reference point 175 connects the Subscription Profile RepositorySPR 180 and the PCRF. The Sp reference point allows the PCRF to requestsubscription information related to the IP-CAN transport level policiesfrom the SPR based on a subscriber ID, a Packet Data Network PDNidentifier and possible further IP-CAN session attributes.

The Gy reference point 125 connects the Service Data Flow Based CreditControl component 110 of an Online Charging System OCS 105 and the PCEF.The Gy reference point allows online credit control for service dataflow based charging.

The Gz reference point 140 connects the PCEF and the Offline ChargingSystem OFCS 145 and enables transport of service data flow based offlinecharging information.

FIG. 2 is a message sequence chart showing an IP-CAN sessionestablishment procedure according to the prior art 3GPP TS 23.203V10.2.1 (2011-01).

In step 201 the gateway GW control session is established for the user.

The Policy Control Enforcement Function PCEF of the gateway GW(PCEF)receives a request for IP-CAN bearer establishment in step 202 followingwhich the GW(PCEF) accepts the request and assigns an IP address for theuser.

The PCEF determines that Policy and Charging Control PCC authorizationis required and requests the authorization of allowed service(s) and PCCrules information from the PCRF in step 203.

In step 206 PCRF then makes the authorization and policy decision.

In step 207 the PCRF sends the decision(s), including a chosen IP-CANbearer establishment mode, to the PCEF where after the GW(PCEF) enforcesthe decision.

If online charging is applicable, and at least one PCC rule wasactivated, the PCEF activates the online charging session, and providerelevant input information for the OCS decision in step 208 whereby theOCS provides the possible credit information to the PCEF in step 209.

If at least one PCC rule was successfully activated and if onlinecharging is applicable, and credit was not denied by the OCS, theGW(PCEF) acknowledges the received IP-CAN bearer establishment requestin step 210.

In steps 211 the IP-CAN bearer signaling is initiated and the sessionestablishment is acknowledged in step 212.

FIG. 3 is a block diagram showing a PCC architecture according to anexemplary embodiment of the invention allowing a user equipment UE 390access to a Packet Data Network PDN 395 via an IP Connectivity AccessNetwork IP-CAN 385, e.g. GPRS.

The Rx reference point 365 connects the Application Function AF 370 andthe Policy and Charging Rules Function PCRF 320. This reference pointenables transport of application level session information from AF toPCRF

The Gx reference point 350 connects the Policy and Charging EnforcementFunction PCEF 330 of a gateway 335, e.g. a GPRS Gateway Support NodeGGSN, and the PCRF and enables a PCRF to have dynamic control over thePCC behavior at a PCEF. The Gx reference point enables the signaling ofPCC decisions, which governs the PCC behavior.

The Gxx reference point 355 connects the Bearer Binding and EventReporting Function BBERF 360 and the PCRF. The Gxx reference pointenables a PCRF to have dynamic control over the BBERF behavior.

The Sp reference point 375 connects the Subscription Profile RepositorySPR 380 and the PCRF. The Sp reference point allows the PCRF to requestsubscription information related to the IP-CAN transport level policiesfrom the SPR based on a subscriber ID, a Packet Data Network PDNidentifier and possible further IP-CAN session attributes.

The Gy reference point 325 connects the Service Data Flow Based CreditControl component 310 of an Online Charging System OCS 305 and the PCEF.The Gy reference point allows online credit control for service dataflow based charging.

The Gz reference point 340 connects the PCEF and the Offline ChargingSystem OFCS 345 and enables transport of service data flow based offlinecharging information.

In order to provide policy information valid for a Gx 350 session toPCRF 320 based on information available in OCS 305 (information likeproduct offerings, time of day based tariff, usage, location etc.) aninterface Sy 315 between PCRF and OCS is introduced.

The Sy interface may use existing Diameter base (RFC 3588) and DiameterCredit Control DCC commands (RFC 4006) such as Credit Control Request(CCR), Credit Control Answer (CCA), Re-Authorization Request (RAR) andRe-Authorization Answer (RAA).

The protocol implemented on the Sy interface supports for examplesending a Network Traffic Policy Profile NTPP or a parameter identifyingsuch an NTPP stored in a NTPP Entity 322 accessible by the PCRF, asanswer to a request from the PCRF.

In the OCS a Policy Data Definition PDD is created in a Determinationmodule DU 307 of the OCS. Based on a configuration of selection rules ofthe PDD, e.g. selection trees, an NTTP and optionally additional NTPPattributes will be determined by the DU when traversing the selectionrules. Thus, in one alternative solution a special rule set separatefrom the rating rule set, e.g. a special network traffic policy profilerule tree, is introduced in DU for policy profile determination. Thispolicy profile rule tree may then be used for deciding policy both at Syrequests and when rechecking policy after a Gy request.

The NTPP may thus be determined by the policy rule tree, where forexample subscriber group defined by Service Class and Offers data areprovisioned, and these data can thereby be used to affect the NTPP beingselected by being part of the conditions in the policy rule treestructure.

The PCRF uses the chosen NTPP and attributes to set the Quality ofService QoS for a data session.

Data used to determine policy is analyzed by the OCS both at requestsreceived via Sy and Gy interface. Due to this policy data determinationmay be based on parameters available on both protocols.

For example, the following parameters are common to both protocols:

-   -   3GPP-Mobile Station MS-TimeZone    -   3GPP-Radio Access Technology RAT-Type    -   3GPP-Serving GPRS Support Node SGSN-Address    -   3GPP-SGSN-Mobile Country Code MCC-Mobile Network Code MNC    -   3GPP-User-Location-Info    -   Called-Station-ID    -   User-Equipment-Info

A request for NTPP determination from the PCRF to the OCS, e.g. aDiameter CCR Initial (See RFC 4006), over Sy may support conveying thefollowing parameters:

-   -   Subscriber-Id    -   SGSN-Address, used for deciding the NTPP and attributes in DU    -   SGSN-MCC-MNC (identifies PLMN), used for deciding the NTPP and        attributes in DU    -   User Location Information, used for deciding the NTPP and        attributes in DU    -   MS-Time-Zone, used for deciding the NTPP and attributes in DU    -   Access Network Charging Identifier Gx and Access Network        Charging Address, used for correlation of Sy and Gy sessions in        OCS.

An interface module 308 is used to communicate with other function unitse.g. PCRF over Sy or PCEF over Gy. The interface module may comprise aLAN/WAN interface or a local connection or bus connecting the OCS tofunctional units of other physical nodes. The interface module may alsocomprise a software unit allowing communication with logical functionalunits residing on the same physical node.

FIG. 4 is a block diagram showing a PCC architecture where exemplaryembodiments of the invention is useful.

Following a policy decision request 405 received over Sy 315 viainterface module 308 an Mobile Subscriber ISDN Number MSISDN e.g.123456789 received in the request is used to access subscriber relateddata from a database 420 of the DU 307. Access to subscriber relateddata may include determining service packages as offers subscribed to,e.g. a service “data gold” with the identifier “400”, accumulator valuesstoring subscriber parameters, subscriber group data as service classe.g. “Normal Subscriber” etc.

Other subscriber identifiers than MSISDN (E.164) is possible, e.g.International Mobile Subscriber Identity IMSI (E.212), Session InitiatedProtocol—Uniform Resource Locator SIP-URI (RFC 3261), Network AccessIdentifier NAI (RFC 2486) and PRIVATE. In one exemplary solution theidentifications are processed in the order that they appear in the idreceived. The first id that results in “subscriber found” in thedatabase 420 may be used.

The DU 307 holds a Policy Data Definition PDD 410 which may define aplurality of service package products, e.g. the “data gold” productoffer “400” offering the user a fixed usage allowance with a higher QoSand when such usage allowance has been consumed the user may continueservices with a lower QoS.

Using the subscriber's static or near static data retrieved from thedatabase 450 possibly augmented with dynamic data received via therequest 405 the NTPP is determined by applying the selection rules ofthe PDD 410. E.g. specific NTPP identification “100” is determined.Optionally one or a plurality of additional policy attributes may alsobe determined by the PDD.

A response message 415 containing the NTPP identifier and optionalattributes is then transmitted to the PCRF via interface module 308. Theidentifier identifies the corresponding NTTP 450 in the PCRF 320 whichmay define attributes such as uplink bit rate, downlink bit rate,priority etc set to specific values.

In one solution, the response message may comprise a plurality ofidentifiers identifying a plurality of network traffic policy profilesand a priority value indicating which NTPP to apply when several areapplicable to the service.

In a further possible solution, the interface Sy provides for theresponse message to convey a NTTP including the NTTP identity, shouldthe profile not be available to the PCRF.

The policy attribute(s), which can be added to the NTPP, can be used toextend the NTPP with more dynamic information. An example of this isthat an attribute indicates if a subscriber has consumed more or lessthan the data volume included in a subscription per month.

The policy attribute may also be used to indicate that though thesubscriber is a “Normal Subscriber” s(he) has bought a specific service,like a music streaming service, and is entitled to a dedicated bearerfor that or otherwise be controlled separately from other traffic withinthe traffic flow.

The determined NTPP will represent the current policy that is valid forthe subscriber at the moment for the request, or in case of time of dayconditions as specified by a rule activation and deactivation times.

To minimize request peaks from the PCRF towards the OCS due to policyswitches due to time of day conditions a rule activation anddeactivation time may be included in the response message to the PCRF.By including two NTPP identifiers in an answer it will be possible toindicate policy before and after a time of day controlled policy switch.If more than one NTPP identifier is included in an answer a ruleactivation respective deactivation time parameter should preferably beincluded to indicate the policy active at any moment in time.

A revalidation time parameter may further be added to the response 415used to indicate when the PCRF at the latest must request a new policydecision. The revalidation time parameter may be controlled from thepolicy decision tree.

Thus, the NTTP identifier, and where applicable the additional policyattributes, rule activation time, rule de-activation time, revalidationtime, priority and additional NTTP identifier is responded back to thePCRF in answer 415.

FIG. 5 is a message sequence chart showing a method for controllingservices in a communication network according to an exemplary embodimentof the invention.

In step 505 a Packet Data Protocol PDP context activation triggers thePCEF 330 of the gateway, e.g. GGSN, 335 to request authorization bysending request for service traffic control as a CCR Initial requestincluding for example MSISDN, QoS-Information, Charging Id, SGSN-adress,SGSN-MCC-MNC, User-Location, Time-Zone etc to the PCRF 320.

The OCS receives the Sy CCR Initial request from the PCRF in step 510.In one possible solution the request may include an access networkcharging address and an access network charging identifier, e.g. anAccess-Network-Charging-Identifier-Gx. Parameters in the Sy CCR Initialmay include MSISDN, Charging Id, SGSN-Address, SGSN-MCC-MNC, UserLocation, Time Zone etc.

An advantage with including the two parameter pairs access networkcharging address and access network charging identifier in the Sy CCRestablishment to the OCS it will be possible to connect the Gx and Gysessions via the Sy session. Hence have the possibility to at an accountchange due to a Gy CCR trigger the corresponding Gx session for a QoSre-authentication by sending a Sy RAR to the PCRF.

In step 511, using the MSISDN, a subscriber account and associatedservice packages are identified.

An analysis is done if Access-Network-Charging-Address-Gx is received inthe CCR Initial in step 513 and is in such case stored together with anSy Session Id.

If Access-Network-Charging-Address-Gx is not received over Sy in the CCRInitial, MSISDN/IMSI and Sy Session ID is stored. Data from the Syrequest is stored for later usage for Gy session and Re-AuthorizationRequest RAR.

The DU 307 of the OCS is then interrogated for policy determination.Parameters that may be included in the Sy CCR Initial and used in thepolicy determination are

-   -   3GPP-MS-TimeZone    -   3GPP-RAT-Type    -   3GPP-SGSN-Address    -   3GPP-SGSN-MCC-MNC    -   3GPP-User-Location-Info    -   Called-Station-ID    -   RAT-Type    -   User-Equipment-Info

The values to use for each parameter may be taken from the latestrequest where they were included, i.e. the values used in a policydecision can come from a mix of Sy and Gy requests.

The network traffic policy profile and attributes associated with theaccount is then determined based on the data received in the requestand/or account data and stored. Examples of account data are servicepackages or subscriber group data, e.g. Service Class, associated withthe account.

In step 515 the OCS sends a policy control command over Sy as a CCAInitial response to the PCRF including an NTTP identifier as policy dataand optionally an event trigger.

The identifier is identifying a network traffic policy profile stored ina network traffic policy profile entity so that it may be applied incontrolling the service.

In step 520 the received policy data, e.g. NTPP identifier, is evaluatedby the PCRF to obtain policy parameters stored in the NTTP Entityidentified by the identifier.

In step 525 the PCRF responds with a CCA Initial over Gx to the PCEFproviding the policy information, e.g. QoS parameters and event trigger.

In step 540 a credit control request is received from a packet gatewayand includes a packet gateway address and a charging identity. Thecredit control request may be a CCR Update over Gy received from a GGSNwhere the packet gateway address is a 3GPP-GGSN-Adress and the chargingidentity is a 3GPP-Charging-Id. The request may include MSISDN,Charging-Id, MSCC, Requested Service Units RSU and used units.

In step 545 the DU determines an account to charge for the service andperforms rating of the services.

In step 550 the OCS sends Granted Service Units GSU to the GGSN in a CCAUpdate over Gy.

In step 560 the following analysis is done in OCS:

If Charging ID or MSISDN/IMSI received in the Gy CCR Update exists, theDU 307 is interrogated for corresponding Sy session. This is done inorder to get more accurate policy analysis in DU by considering Gydynamic data like location, SGSN address etc.

The access network charging addresses is matched with the packet gatewayaddress and the access network charging identifier is matched with thecharging identity to determine that the received requests for servicetraffic control and credit control relates to the same service instance.

In one embodiment it is determined that the received requests forservice traffic control over Sy and credit control request over Gyrelates to the same service instance by matching the IMSI and/or MSISDNreceived in the request for service traffic control with the IMSI and/orMSISDN received in the request for credit control;

It is checked if the account to charge differs from the accountdetermined in step 511.

Thereafter, the DU is interrogated for policy, i.e. NTPP, determination.The DU determines based on the received data and the predefined set ofrules, a network traffic policy profile associated with the determinedaccount to charge. The DU does policy analysis based on dynamic datareceived (like location, time zone, SGSN address etc). Upon receivinganswer from DU with policy data the OCS compares the policy datareceived from DU with policy data stored. If these differ, a RAR towardsPCRF should be initiated and new policy data should be stored.

Thus, after each Gy request a new policy decision may be made to checkif the present policy has changes due to Used-Service-Units from the Gyrequest, due to other events on the account or changes on the UE'sattributes (radio access type, location, etc.).

The OCS may save all Sy parameters, per session, that are available asconditions in the policy determination so that they can be used atpolicy re-evaluation following a Gy request.

In step 565 the CCN initiates sending of Sy RAR to the PCRF includingthe new policy data, i.e. NTPP identifier, to be applied in controllingthe service.

In step 570 the OCS receives a RAA over Sy.

In step 575 the DU performs analysis if the change of policy should benotified to end user by sending Unstructured Supplementary Service DataUSSD or Short Message Service SMS message e.g. information that athreshold is passed.

In step 580, if applicable, the OCS initiates the notification towardsthe user using e.g. USSD or SMS.

In step 585 the PCRF makes the policy evaluation based on theinformation received from OCS.

If the policy, i.e. NTPP and/or attributes, is changed the PCRFinitiates RAR with new QoS in step 590 to the PCEF over Gx.

In step 595 PCEF acknowledges using RAA.

Additionally, the described solution may advantageously be used where,instead of being triggered by the PCRF in step 510, the triggering isreceived as a CCR Initial from the PCEF over Gy, or as a CCR Updatereceived over Gy allowing the OCS to initiate the session to provisionan NTPP identifier to PCRF when spending limits are reached mid-session.Re-authorization procedure (RAR/RAA) initiated from OCS may be used forthis.

FIG. 6 is a flow chart showing an exemplary embodiment of a method forcontrolling services in a communication network according to theinvention. In step 610 the OCS receives a request for service trafficcontrol identifying a first account. A service package associated withthe account is identified in step 620. In step 630 a first networktraffic policy profile is determined which the OCS transmits as a firstpolicy control command in step 640.

In step 645 a request for credit control of a service is received. Asecond account to charge for service is determined in step 650. In step655 it is checked if the request for service traffic control and therequest for credit control relates to the same service instance.

If the check is confirming that the request for service traffic controland the request for credit control relates to the same service instancethe method continues in step 660 with checking if the first accountdiffers from the second account.

If the first and second differs, the method continues in step 665 withdetermining a second network traffic policy applicable for the secondaccount.

In step 670 as second policy control command is transmitted identifyinga second NTPP.

FIG. 7 is a block diagram showing relations between service packageproducts and network traffic policy profiles according to an exemplaryembodiment of the invention.

Network Traffic Policy Profile NTPPs such as “100” 710 and “20” 720 arestored in the PCRF 320 while product offers as service package productsare stored with the OCS 305. By identifying a user's service packageproduct the relevant NTPP is identified and a parameter identifying thisprofile may be transmitted to the PCRF 320 over the interface Sy 315.

A Network Traffic Policy Profile NTPP “100” 710 including policyparameters such as access control, header enrichment, routing rules,transmission speed—e.g. 10 Mbit/s may be associated with several servicepackage products for example a Bonus Day 750, Gold 730, Business 740 orTurbo 770 offers. Correspondingly, a service package product 730 mayutilize several NTPPs “100” 710 and “20” 720 to be applied depending one.g attributes 780.

In addition, attributes 780 are utilized to limit the number of NTPPsneeded. For a certain parameter in the NTPP, e.g. bandwidth, theparameter's value is represented in the attribute. This enables a changeof attribute parameter value, without the need to change NTPP.

FIG. 8 is a block diagram showing an exemplary computing device forimplementing a system for controlling services in a communicationnetwork according to an exemplary embodiment.

FIG. 8 illustrates an example of a suitable computing system environment800 in which the claimed subject matter can be implemented, although asmade clear above, the computing system environment 800 is only oneexample of a suitable computing environment for an Online ChargingSystem and is not intended to suggest any limitation as to the scope ofuse or functionality of the claimed subject matter. Further, thecomputing environment 800 is not intended to suggest any dependency orrequirement relating to the claimed subject matter and any one orcombination of components illustrated in the example operatingenvironment 800.

Looking now to FIG. 8, an example of a device for implementing thepreviously described invention includes a general purpose computingdevice in the form of a computer 810. Components of computer 810 caninclude, but are not limited to, a processing unit 820, a system memory830, and a system bus 821 that couples various system componentsincluding the system memory to the processing unit 820. The system bus821 can be any of several types of bus structures including a memory busor memory controller, a peripheral bus, and a local bus using any of avariety of bus architectures.

Computer 810 can include a variety of computer readable media. Computerreadable media can be any available media that can be accessed bycomputer 810. By way of example, and not limitation, computer readablemedia can comprise computer storage media and communication media.Computer storage media includes volatile and nonvolatile as well asremovable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CDROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media can embody computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and can include any suitable information delivery media.

The system memory 830 can include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) and/orrandom access memory (RAM). A basic input/output system (BIOS),containing the basic routines that help to transfer information betweenelements within computer 810, such as during start-up, can be stored inmemory 830. Memory 830 can also contain data and/or program modules thatare immediately accessible to and/or presently being operated on byprocessing unit 820. By way of non-limiting example, memory 830 can alsoinclude an operating system, application programs, other programmodules, and program data.

In one embodiment of the invention the Interface Module 308 is afunction block loaded in the memory and processable by the processingunit whereby the OCS is having the ability to receive a request forservice traffic control, the request including at least data identifyinga first communication network account and the Determination Module 307is a function block loaded in the memory and processable by theprocessing unit whereby the OCS is having the ability to determine,based on the received data and a predefined set of rules, a firstnetwork traffic policy profile associated with the first account. TheInterface Module function block further has the ability to transmit to aPolicy and Charging Rules Function PCRF a first policy control commandincluding an identifier identifying the first network traffic policyprofile stored in an network traffic policy profile entity, to beapplied in controlling the service.

The computer 810 can also include other removable/non-removable andvolatile/nonvolatile computer storage media. For example, computer 810can include a hard disk drive that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive thatreads from or writes to a removable, nonvolatile magnetic disk, and/oran optical disk drive that reads from or writes to a removable,nonvolatile optical disk, such as a CD-ROM or other optical media. Otherremovable/non-removable, volatile/nonvolatile computer storage mediathat can be used in the exemplary operating environment include, but arenot limited to, magnetic tape cassettes, flash memory cards, digitalversatile disks, digital video tape, solid state RAM, solid state ROMand the like. A hard disk drive can be connected to the system bus 821through a non-removable memory interface such as an interface, and amagnetic disk drive or optical disk drive can be connected to the systembus 821 by a removable memory interface, such as an interface.

A user can enter commands and information into the computer 810 throughinput devices such as a keyboard or a pointing device such as a mouse,trackball, touch pad, and/or other pointing device. Other input devicescan include a microphone, joystick, game pad, satellite dish, scanner,or similar devices. These and/or other input devices can be connected tothe processing unit 820 through user input 840 and associatedinterface(s) that are coupled to the system bus 821, but can beconnected by other interface and bus structures, such as a parallelport, game port or a universal serial bus (USB).

A graphics subsystem can also be connected to the system bus 821. Inaddition, a monitor or other type of display device can be connected tothe system bus 821 through, an interface, such as output interface 850,which can in turn communicate with video memory. In addition to amonitor, computers can also include other peripheral output devices,such as speakers and/or printing devices, which can also be connectedthrough output interface 850.

The computer 810 can operate in a networked or distributed environmentusing logical connections to one or more other remote computers, such asremote server 870, which can in turn have media capabilities differentfrom device 810. The remote server 870 can be a personal computer, aserver, a router, a network PC, a peer device or other common networknode, and/or any other remote media consumption or transmission device,and can include any or all of the elements described above relative tothe computer 810. The logical connections depicted in FIG. 8 include anetwork 871, such as a local area network (LAN) or a wide area network(WAN), but can also include other networks/buses.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 860. When used ina WAN networking environment, the computer 810 can include acommunications component, such as a modem, or other means forestablishing communications over a WAN, such as the Internet. Acommunications component, such as a modem, which can be internal orexternal, can be connected to the system bus 821 through the user inputinterface at input 840 and/or other appropriate mechanism.

In a networked environment, program modules depicted relative to thecomputer 810, or portions thereof, can be stored in a remote memorystorage device. It should be noted that the network connections shownand described are exemplary and other means of establishing acommunications link between the computers can be used.

Additionally, it should be noted that as used in this application, termssuch as “component,” “display,” “interface,” and other similar terms areintended to refer to a computing device, either hardware, a combinationof hardware and software, software, or software in execution as appliedto a computing device. For example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program and a computingdevice. As an example, both an application running on a computing deviceand the computing device can be components. One or more components canreside within a process and/or thread of execution and a component canbe localized on one computing device and/or distributed between two ormore computing devices, and/or communicatively connected modules.Further, it should be noted that as used in this application, terms suchas “system user,” “user,” and similar terms are intended to refer to theperson operating the computing device referenced above.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” includes any andall combinations of one or more of the associated listed items.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated.

Finally, other blocks may be added/inserted between the blocks that areillustrated. Moreover, although some of the diagrams include arrows oncommunication paths to show a primary direction of communication, it isto be understood that communication may occur in the opposite directionto the depicted arrows.

Many different embodiments have been disclosed herein, in connectionwith the above description and the drawings. It will be understood thatit would be unduly repetitious and obfuscating to literally describe andillustrate every combination and subcombination of these embodiments.Accordingly, the present specification, including the drawings, shall beconstrued to constitute a complete written description of variousexemplary combinations and subcombinations of embodiments and of themanner and process of making and using them, and shall support claims toany such combination or subcombination.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present invention.All such variations and modifications are intended to be included hereinwithin the scope of the present invention.

1. A method for operating an online charging system to control servicetraffic in a communication network, the method comprising steps of:receiving a request for service traffic control, the request includingat least data identifying a first communication network account;determining, based on the received data and a predefined set of rules, afirst network traffic policy profile associated with the first account;transmitting to a Policy and Charging Rules Function PCRF a first policycontrol command including an identifier identifying the first networktraffic policy profile stored in an network traffic policy profileentity, to be applied in controlling the service.
 2. A method accordingto claim 1 wherein: before the step of determining a network trafficpolicy profile determining, based on the received data, a servicepackage associated with said account to which said service relates; andwherein the step of determining the network traffic policy profilecomprises the determination being based on an association between saidservice package and the network traffic policy profile.
 3. A methodaccording to claim 1 wherein the received request for service trafficcontrol further includes a first subscriber identity and the methodfurther comprises the steps: receiving from a Packet Gateway a requestfor credit control of a service including a second subscriber identity;determining, using the second subscriber identity, a second account tocharge for the service; determining that the received requests forservice traffic control and credit control relates to the same serviceinstance by matching the first and second subscriber identity;determining that the second account to charge differs from the firstaccount; determining, based on the received data and the predefined setof rules, a second network traffic policy profile associated with thesecond account; and transmitting to the PCRF a second policy controlcommand including an identifier identifying the second network trafficpolicy profile stored in a second network traffic policy profile entity,to be applied in controlling the service.
 4. A method according to claim1, wherein the received request for service traffic control furtherincludes an access network charging address and an access networkcharging identifier, and the method further comprises the steps:receiving from a Packet Gateway a request for credit control of aservice including a packet gateway address and a charging identity;determining a second account to charge for the service; determining thatthe received requests for service traffic control and credit controlrelates to the same service instance by matching the access networkcharging addresses with the packet gateway address and matching theaccess network charging identifier with the charging identity;determining that the second account to charge differs from the firstaccount; determining, based on the received data and the predefined setof rules, a second network traffic policy profile associated with thesecond account; and transmitting to the PCRF a second policy controlcommand including an identifier identifying the second network trafficpolicy profile stored in a second network traffic policy profile entity,to be applied in controlling the service.
 5. A method according to claim3 wherein the identifier identifying the second network traffic policyprofile is sent as a DIAMETER Re-Authentication-Request.
 6. A methodaccording to claim 1 wherein the step of determining a first and/orsecond network traffic policy profile is further based on account data.7. A method according to claim 6 wherein the account data comprises dataidentifying subscriber group and/or data specifying services associatedwith the account.
 8. A method according to claim 3 wherein the step ofdetermining a first and/or second network traffic policy profile isfurther based on data received from the Packet Gateway in the requestfor credit control.
 9. A method according to claim 1 wherein the networktraffic policy profile contains a quality of service parameter ofbandwidth and/or priority that is to a particular value.
 10. A methodaccording to claim 1 wherein the network traffic policy profile containsat least a parameter indicating that a type of traffic within a trafficflow should be service traffic controlled separately from other trafficwithin the traffic flow.
 11. A method according to claim 1 wherein thenetwork traffic policy profile is associated with one or more servicepackages.
 12. A method according to claim 1 wherein a service package isassociated with several network traffic policy profiles.
 13. A methodaccording to claim 1 wherein the step of transmitting a policy controlcommand further comprises determining if the identified NTPP is storedin the NTPP Entity, and if not, transmitting said NTTP to the PCRF forstorage in the NTTP entity.
 14. A method according to claim 1 whereinthe request for service traffic control is a Diameter Credit ControlRequest command.
 15. A method according to claim 1 wherein the policycontrol command further comprises a network traffic policy profileactivation and/or deactivation time parameter.
 16. A method according toclaim 1 wherein the policy control command further comprises anindicator indicating that resources beyond or below a threshold has beenconsumed from the account.
 17. A method according to claim 1 wherein thepolicy control command further comprises a revalidation time indicatingwhen the PCRF must send a new request for service traffic control.
 18. Amethod according to claim 1 wherein the first policy control commandfurther comprises a plurality of identifiers identifying a plurality ofnetwork traffic policy profiles and a priority value indicating whichnetwork traffic policy profile to apply when several are applicable tothe service.
 19. An online credit control system for controlling servicetraffic in a communication network, the online credit control systemcomprising: an interface module adapted for receiving a request forservice traffic control, the request including at least data identifyinga first communication network account; a determination module adaptedfor determining, based on the received data and a predefined set ofrules, a first network traffic policy profile associated with the firstaccount; the interface module further adapted for transmitting to aPolicy and Charging Rules Function PCRF a first policy control commandincluding an identifier identifying the first network traffic policyprofile stored in an network traffic policy profile entity, to beapplied in controlling the service.
 20. An online credit control systemaccording to claim 19 wherein the determination module is furtheradapted to: before carrying the determining the first network trafficpolicy profile, determining based on the received data a service packageassociated with said account to which said service relates; and whereindetermining the first network traffic policy profile is carried outbased on an association between said service package and the networktraffic policy profile.
 21. An online credit control system according toclaim 19 wherein the received request for service traffic controlfurther includes an access network charging address and an accessnetwork charging identifier, and the system further comprises: theinterface module adapted for receiving from a Packet Gateway a requestfor credit control of a service including a packet gateway address and acharging identity; the determination module adapted for: determining asecond account to charge for the service; determining that the receivedrequests for service traffic control and credit control relates to thesame service instance by matching the access network charging addresseswith the packet gateway address and matching the access network chargingidentifier with the charging identity; determining that the secondaccount to charge differs from the first account; determining, based onthe received data and the predefined set of rules, a second networktraffic policy profile associated with the second account; and theinterface module adapted for transmitting to the PCRF a second policycontrol command including an identifier identifying the second networktraffic policy profile stored in a second network traffic policy profileentity, to be applied in controlling the service.
 22. An online creditcontrol system according to claim 21 wherein the determining a firstand/or second network traffic policy profile is further based on datareceived from the Packet Gateway in the request for credit control. 23.An online credit control system according to claim 19 wherein thenetwork traffic policy profile contains at least a parameter indicatingthat a type of traffic within a traffic flow should be service trafficcontrolled separately from other traffic within the traffic flow.
 24. Anonline credit control system according to claim 19 wherein the networktraffic policy profile is associated with one or more service packages.25. An online credit control system according to claim 19 wherein aservice package is associated with several network traffic policyprofiles.
 26. An online credit control system according to claim 19wherein the policy control command further comprises a network trafficpolicy profile activation and/or deactivation time parameter.
 27. Anonline credit control system according claim 19 wherein the policycontrol command further comprises a revalidation time indicating whenthe PCRF must send a new request for service traffic control.
 28. Anonline credit control system according to claim 19 wherein the firstpolicy control command further comprises a plurality of identifiersidentifying a plurality of network traffic policy profiles and apriority value indicating which network traffic policy profile to applywhen several are applicable to the service.